Skip to content

Apply instance name rules when renaming an instance - #9127

Merged
n-lark merged 4 commits into
mainfrom
188-rename-name-validation
Nov 9, 2026
Merged

n-lark merged 4 commits into
mainfrom
188-rename-name-validation

Conversation

@n-lark

@n-lark n-lark commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Description

Renaming an instance through the update endpoint now uses the same name rules as creating one. Names that would be rejected at create are now rejected on rename with the same invalid_project_name error.

Updates two existing rename tests that used names with spaces, and adds a test for invalid names.

Related Issue(s)

Resolves https://github.com/FlowFuse/security/issues/188

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
  • Link to Changelog Entry PR, or note why one is not needed.

Labels

  • Includes a DB migration? -> add the area:migration label

@n-lark
n-lark requested review from Steve-Mcl and andypalmi November 6, 2026 16:13
@n-lark n-lark self-assigned this Nov 6, 2026
@codecov

codecov Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.03%. Comparing base (b56aad2) to head (18fd0df).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9127   +/-   ##
=======================================
  Coverage   80.03%   80.03%           
=======================================
  Files         476      476           
  Lines       26212    26216    +4     
  Branches     6981     6982    +1     
=======================================
+ Hits        20979    20983    +4     
  Misses       5233     5233           
Flag Coverage Δ
backend 80.03% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@andypalmi andypalmi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, two small nits inline.

Comment thread forge/routes/api/project.js Resolved
n-lark and others added 2 commits November 9, 2026 11:26
Co-authored-by: Andrea Palmieri <76187074+andypalmi@users.noreply.github.com>
@n-lark
n-lark enabled auto-merge (squash) November 9, 2026 19:31
@n-lark
n-lark merged commit c9beb5f into main Nov 9, 2026
30 of 31 checks passed
@n-lark
n-lark deleted the 188-rename-name-validation branch November 9, 2026 19:40

This branch was previously deployed

1 inactive deployment
staging — 18fd0dfc Deployed Nov 9, 2026 by n-lark via Remove application #12954
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants